Add missing root module dependencies - #1000
Open
piotrfila wants to merge 3 commits into
Open
Conversation
mattnite
force-pushed
the
passthrough-modules
branch
from
August 9, 2026 02:01
bf24e59 to
cde489c
Compare
mattnite
force-pushed
the
passthrough-modules
branch
from
August 9, 2026 03:54
cde489c to
9d672a5
Compare
Contributor
|
I chatted to a friend outside the project about this, and ultimately I think we need to return to creating tarballs, but generating them far more often (like every push to main). This gets us the lazy dependencies and the standalone modules. It's either that or we contribute package manager features to Zig. |
mattnite
requested changes
Aug 9, 2026
Contributor
Author
|
@mattnite Is this what you have in mind? |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Right now it's a bit cumbersome to use one of microzig's modules - you have to clone the repo locally or add it as a git submodule and import it by path.
This PR exports all the modules in the root build.zig.
I'm not sure if updating all of microzig to import modules through the root project is a good idea - if we leave the imports as they are (by path) it's easier to override them for development (with zig command line options).
Also, I still need to find a good way to re-export libraries, not just modules